home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980901-19981211
/
000182_news@newsmaster….columbia.edu _Thu Oct 22 10:22:43 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA00469
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 22 Oct 1998 10:22:43 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA26721
for kermit.misc@watsun; Thu, 22 Oct 1998 10:22:43 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc,comp.os.linux.misc
Subject: Re: CKermit 6.1beta rpm?
Date: 22 Oct 1998 14:22:42 GMT
Organization: Columbia University
Lines: 59
Message-ID: <70nf3i$oga$1@apakabar.cc.columbia.edu>
References: <7093jk$hpl$1@eskinews.eskimo.com> <70ju4k$567$1@eskinews.eskimo.com> <70kpvd$7mu$1@apakabar.cc.columbia.edu> <70lk07$4qb$1@eskinews.eskimo.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:9378 comp.os.linux.misc:303582
In article <70lk07$4qb$1@eskinews.eskimo.com>,
Jim Osborn <jimo@eskimo.com> wrote:
: ...
: Thanks for illuminating some of the frustrations of keeping up with
: the various changes. In particular, the details of dealing with
: things like hardware flow control sound worth my following up on.
:
I'd still like confirmation that C-Kermit 6.1 Beta can be built "out of the
box" on Red Hat, Slackware, Debian, SuSE, Caldera, and any other Linux
distributions I might not know about, and various versions of each, and if
not, what the error messages are or what changes had to be made to Kermit
itself, or what symlinks had to be installed, etc. Instructions:
$ mkdir kermit
$ cd kermit
$ ftp kermit.columbia.edu
user: anonymous
password: your-email-address
ftp> cd kermit/test/bin
ftp> binary
ftp> get cku193.tar.gz
ftp> bye
$ gunzip cku193.tar.gz
$ tar xvf cku193.tar
$ make linux
Please send me note stating the Linux package name and version (e.g. Red Hat
5.1), the hardware platform (PC, Alpha, Sparc, etc), and the results of the
build (success, or failure with messages).
I already know it is OK on Red Hat 5.1 (PC and Alpha), and on the Amiga
(Red Hat 5.0).
Thanks!
: Now if I can just figure out where these beeps come from whenever
: a script writes to the screen... :)
:
Beeps come from:
a. Syntax error messages (when an invalid command is included in the
script). Cure: fix the syntax errors.
b. BEL characters coming from the host and displayed locally during INPUT /
MINPUT when INPUT ECHO is ON. Cure: SET INPUT ECHO OFF.
c. Completion of file transfer. To defeat: SET TRANSFER BELL OFF.
d. Explicit "printing" of BEL characters by your script, using the
BEEP command or by including \7 in an ECHO string, etc. But if you
had done this, you would expect some beeps.
Of course other beeps are possible during interactive use: the ones that
come from host in CONNECT (terminal) mode, the ones you get by trying to
complete a command field that is invalid or insufficiently specified, or by
trying to delete past the beginning of the command buffer, or by trying to
recall commands beyond the boundaries of the recall buffer, etc.
- Frank